Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Using the class and entity cache

The major cost of class and entity cache is in the deployment overhead. If you change class attribute defaults, extend the class hierarchy, add new attributes, or change the application database schema, you must regenerate and redeploy the class and entity cache to each client.

If you have generated the cache using the Generate Client Cache tool or you have set the auto_dump_entity_cache session property to YES, any changes you make to the entity (schema tables) and class data (including adding of new properties or changing the defaults for the class data) in design-time sessions require that you update the cache for all clients. If you do not regenerate the cache using the Generate Client Cache tool and deploy the regenerated cache appropriately, none of your changes will be visible on the affected clients.